feat: implement catalog search and sorting persistence in URL #117
+222
−30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Search queries, filters, and sorting were stored in local React state, so users lost their selected settings when refreshing the page or navigating away, and could not share filtered results. This PR stores them in URL query parameters.
Changes
useCatalogParamshook (frontend/src/hooks/useCatalogParams.ts) that reads and writessearch,category,sortByandsortDirectionin the URL. Invalid values are ignored.searchstate and thekey={search}workaround fromApp.tsx; the header search now navigates to/explore?search=…, soNavBarno longer takes anonSearchprop.frontend/src/test/useCatalogParams.test.tsx.Related issues
Closes #94
Verification
Manual testing:
/explore, set a search, category and sort. The URL updates.Checklist